⚠️ Documentation: Misleading command in Local Development workflow\n\nThis docker compose up -d starts ALL services (including the app containers), which conflicts with the stated intent of running Node.js apps locally for hot reload. Having both containerized and local app instances running simultaneously would cause port conflicts.\n\nSuggested fix:\nbash\npnpm docker:db:up\npnpm install\npnpm migrate\npnpm seed\npnpm dev\n\n\nOr use docker compose up postgres -d directly (which is what pnpm docker:db:up does).

💡 Naming: docker:db:down stops all services, not just the database

docker compose down stops and removes all containers in the compose stack (backend, frontend, nginx, postgres), but the docker:db:* namespace implies database-only operations. This is asymmetric with docker:db:up which correctly starts only the postgres service.

Suggested fix — either stop only the postgres service:

"docker:db:down": "docker compose stop postgres"

Or rename to make the broader scope explicit:

"docker:down": "docker compose down"

docker:db:up uses docker compose up postgres -d. Elsewhere in the repo the documented pattern is docker compose up -d postgres (e.g. docs/postgis-address-autocomplete.md), which also matches the canonical CLI syntax. Reordering the args will keep docs consistent and avoid edge-case parsing differences across Docker/Compose versions.

The PR description says docker:down was renamed to docker:db:down (and docker:db is mentioned as the “db only” script), but package.json still defines docker:down and introduces docker:db:up. Either update the scripts to match the documented naming, or adjust the PR description/docs to reflect the actual script names to avoid confusion for contributors.